Test Run War ^^^^^ **Definition:** * Test failures occur at random when several people are running tests simultaneously. **Code Example:** .. code-block:: ruby Suite.run() --> Test 3 fails Suite.run() --> Test 3 crashes Suite.run() --> All tests pass Suite.run() --> Test 3 fails **References:** .. admonition:: Quality attributes * :octicon:`file-code;1em` - Code Example * :octicon:`comment-discussion;1em` - Cause and Effect * :octicon:`graph;1em` - Frequency * :octicon:`sync;1em` - Refactoring * `A survey on test practitioners' awareness of test smells `_ * `An empirical analysis of the distribution of unit test smells and their impact on software maintenance `_ :octicon:`graph;1em` * `An exploratory study of the relationship between software test smells and fault-proneness `_ :octicon:`comment-discussion;1em` :octicon:`graph;1em` * `Are test smells really harmful? An empirical study `_ :octicon:`comment-discussion;1em` :octicon:`graph;1em` :octicon:`sync;1em` * `Automatic generation of smell-free unit tests `_ :octicon:`comment-discussion;1em` * `Categorising Test Smells `_ :octicon:`graph;1em` * `Enhancing developers’ awareness on test suites’ quality with test smell summaries `_ * `How are test smells treated in the wild? A tale of two empirical studies `_ :octicon:`graph;1em` * `On the interplay between software testing and evolution and its effect on program comprehension `_ :octicon:`comment-discussion;1em` * `Refactoring Test Code `_ :octicon:`comment-discussion;1em` :octicon:`sync;1em` * `Refactoring Test Smells With JUnit 5: Why Should Developers Keep Up-to-Date? `_ :octicon:`file-code;1em` :octicon:`comment-discussion;1em` :octicon:`graph;1em` :octicon:`sync;1em` * `Test Smell Detection Tools: A Systematic Mapping Study `_ * `Understanding practitioners’ strategies to handle test smells: a multi-method study `_ :octicon:`comment-discussion;1em` :octicon:`sync;1em` * `xUnit test patterns: Refactoring test code `_ :octicon:`file-code;1em` :octicon:`comment-discussion;1em` :octicon:`sync;1em`